home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20021006-20030409
/
000263_JDanSkinner@JDanSkinner.com_Wed Feb 5 12:03:09 EST 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
2KB
|
48 lines
Article: 14057 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!panix!bloom-beacon.mit.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: JDanSkinner@JDanSkinner.com (Dan Skinner)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Launching K95
Date: 5 Feb 2003 08:32:06 -0800
Organization: http://groups.google.com/
Lines: 29
Message-ID: <8ce22d01.0302050832.24c216b6@posting.google.com>
References: <8ce22d01.0302041515.580c2553@posting.google.com> <OQ00a.9294$KG1.3747787@twister.nyc.rr.com>
NNTP-Posting-Host: 24.159.192.106
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1044462726 18265 127.0.0.1 (5 Feb 2003 16:32:06 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 5 Feb 2003 16:32:06 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14057
I beg to differ. There is a way because it happened.
Perhaps you could provide some detail on "Common Application Directory"?
The script being launched is in c:\k95\scripts, does that have meaning?
The simple question is how do I cause the proper k95.ini to be launched
with k95g.exe ver 2.1.3?
Regards...Dan.
Jeffrey Altman <jaltman@columbia.edu> wrote in message news:<OQ00a.9294$KG1.3747787@twister.nyc.rr.com>...
> There is no way that Kermit could change from one to the other.
> K95 looks in the directory listed in the registry as the Common
> Application Directory first; if it cannot find the K95.INI file there it
> checks the end user's profile directory tree; if it can't find it there
> it checks the K95 exe directory. The order of checks is hardcoded into
> the executable. It is not determined by registry values.
>
>
> Dan Skinner wrote:
> > I was so pleased with myself for making the launch so
> > beautiful. It worked prefectly for (what) 8 days, then
> > it failed to "restore" - remember I stuck it in k95.ini.
> > Some investigation proved that the Kermit (K95 2.1.3 had decided
> > (On its own?) to change from c:\windows\---\k95.ini
> > to c:\k95\k95.ini (left over from 1.1.21.) I copied the new k95.ini
> > to the old location (C:\k95) and all is well, except I have no idea how
> > I caused the change.
> >
> > PS how do I change it back? I did a search of registry without luck.
> >
> > Regards...Dan.